Packet data connectivity control with volume charged service limitation

ABSTRACT

A node of a wireless communication network ( 150; 160; 170; 210; 220; 230; 240 ) receives an indication from a user equipment ( 10 ). The indication indicates that a limitation of volume charged packet data services is required for the user equipment ( 10 ). Depending on the received indication, the node ( 150; 160; 170; 210; 220; 230; 240 ) prevents transmission of packet data associated with the volume charged packet data services and allows transmission of packet data associated with one or more other packet data services.

TECHNICAL FIELD

The present invention relates to methods for packet data connectivityand to corresponding devices.

BACKGROUND

In cellular networks, e.g., as specified by 3GPP (3^(rd) GenerationPartnership Project), a user equipment (UE) may establish a packet dataconnection for utilizing certain packet data services, in particularInternet Protocol (IP) based services. Such services may for example beprovided by the IMS (IP Multimedia Subsystem) as specified in 3GPP TS23.228 V12.4.0 (2014-03).

In the LTE (Long Term Evolution) cellular network technology specifiedby 3GPP, all connectivity is packet based, while other radio accesstechnologies, e.g., 2G technologies such as GSM (Global System forMobile Communications) or 3G technologies such as UMTS (Universal MobileTelecommunication System) also allow circuit switched (CS) connections,e.g., for voice calls or SMS (Short Message Service). In the LTEtechnology, also voice and SMS need to be provided via packet basedconnectivity.

However, usage of packet based connectivity is in some cases not desiredfrom a subscriber perspective. For example, a subscriber may have onlylimited quota for packet data, and exceeding this quota may causeundesired charging. Further, usage of packet based connectivity whileroaming may also result in undesired charging. Accordingly, a commonpractice is to switch the UE in a “data off” state, or “data off whenroaming” state.

On a 2G or 3G access, the selection of “data off” or “data off whenroaming” has the effect of disabling usage all packet data connectivityaccess points, each identified by an APN (Access Point Name), by the UE.Accordingly, no packet data connectivity is established for the UE.

However, on an LTE access suppressing packet data connectivity mayrender the UE unusable. Further, if the UE does not provide an APNduring initial attach, the default APN from the subscription is used toestablish a PDN (Packet Data Network) connection. This might be theInternet APN or another APN which that should not be used when “dataoff” or “data off when roaming” is selected.

Accordingly, there is a need for techniques which allow for efficientlycontrolling packet based connectivity in a wireless communicationnetwork.

SUMMARY

According to an embodiment of the invention, a method of controllingpacket based connectivity in a wireless communication network isprovided. According to the method, a node of the wireless communicationnetwork receives, from a UE, an indication that a limitation of volumecharged packet data services is required for the UE. Depending on thereceived indication, the node prevents transmission of packet dataassociated with the volume charged packet data services and allowstransmission of packet data associated with one or more other packetdata services.

According to a further embodiment of the invention, a method ofcontrolling packet based connectivity in a wireless communicationnetwork is provided. According to the method, a UE detects a command toswitch off packet data connectivity of the UE. In response to thecommand, the UE sends, to the wireless communication network, anindication that a limitation of volume charged packet data services isrequired for the UE.

According to a further embodiment of the invention, a node for awireless communication network is provided. The node comprises at leastone interface. Further, the node comprises at least one processor. Theat least one processor is configured to receive, from a UE, anindication that a limitation of volume charged packet data services isrequired for the UE. Further, the at least one processor is configuredto prevent transmission of packet data associated with the volumecharged packet data services and allow transmission of packet dataassociated with one or more other packet data services. This preventingand allowing is accomplished depending on the received indication.

According to a further embodiment of the invention, a UE is provided.The UE comprises an interface for connecting to a wireless communicationnetwork. Further, the UE comprises at least one processor. The at leastone processor is configured to detect a command to switch off packetdata connectivity of the UE. Further, the at least one processor isconfigured to send to the wireless communication network an indicationthat a limitation of volume charged packet data services is required forthe UE. This sending is accomplished in response to the command.

According to a further embodiment of the invention, a computer programor computer program product is provided, e.g., in the form of anon-transitory storage medium, which comprises program code to beexecuted by at least one processor of a node of a wireless communicationnetwork. Execution of the program code causes the at least one processorto receive, from a UE, an indication that a limitation of volume chargedpacket data services is required for the UE. Further, execution of theprogram code causes the at least one processor to prevent transmissionof packet data associated with the volume charged packet data servicesand allow transmission of packet data associated with one or more otherpacket data services. This preventing and allowing is accomplisheddepending on the received indication.

According to a further embodiment of the invention, a computer programor computer program product is provided, e.g., in the form of anon-transitory storage medium, which comprises program code to beexecuted by at least one processor of a UE. Execution of the programcode causes the at least one processor to detect a command to switch offpacket data connectivity of the UE. Further, execution of the programcode causes the at least one processor to send to the wirelesscommunication network an indication that a limitation of volume chargedpacket data services is required for the UE. This sending isaccomplished in response to the command.

Details of such embodiments and further embodiments will be apparentfrom the following detailed description of embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates an exemplary architecture in whichcontrol of packet data connectivity may be implemented according to anembodiment of the invention.

FIG. 2 schematically illustrates exemplary processes according to anembodiment of the invention.

FIG. 3 schematically illustrates further exemplary processes accordingto an embodiment of the invention.

FIG. 4 schematically illustrates further exemplary processes accordingto an embodiment of the invention.

FIG. 5 shows a flowchart for illustrating a method according to anembodiment of the invention, which for example may be implemented by anIMS node.

FIG. 6 shows a flowchart for illustrating a further method according toan embodiment of the invention, which for example may be implemented bya node controlling handling of user plane data traffic.

FIG. 7 shows a flowchart for illustrating a further method according toan embodiment of the invention, which for example may be implemented bya UE.

FIG. 8 schematically illustrates structures of a node according to anembodiment of the invention, e.g., corresponding to an IMS node.

FIG. 9 schematically illustrates structures of a node according to anembodiment of the invention, e.g., corresponding to a node controllinghandling of user plane data traffic.

FIG. 10 schematically illustrates structures of a UE according to anembodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS

In the following, concepts according to embodiments of the inventionwill be explained in more detail by referring to the accompanyingdrawings. The illustrated concepts relate to control of packet dataconnectivity in a wireless communication network. In the illustratedembodiments, it is assumed that the wireless communication network isbased on the LTE technology as specified by 3GPP. However, it is to beunderstood that the illustrated concepts could be applied in acorresponding manner to other technologies, e.g., GSM, UMTS, orCDMA2000.

The concepts as illustrated in the following are based on an indicationprovided by a UE to the wireless communication network. By means of theindication, the UE can indicate that a limitation of volume chargedpacket data services is required for the UE. The indication has thepurpose of preventing transmission of packet data traffic associatedwith the volume charged packet data services and allowing transmissionof packet data traffic associated with one or more other packet dataservices by one or more nodes the wireless communication network. The UEmay provide this indication when it is in a “data off” state or “dataoff when roaming” state. One or more nodes of the wireless communicationnetwork may react to this indication by taking appropriate measures toprevent the transmission of packet data associated with the volumecharged packet data services and allowing the transmission of the packetdata traffic associated with the one or more other packet data services.For example, a node which is responsible for providing a service to theUE may reject a request associated with the service or inactivate avolume charged component of the service. Further, a node which isresponsible for controlling handling of user plane traffic of the UE mayapply a policy, e.g., in the form of a packet filter, which blocks thepacket data traffic associated with the volume charged services andallows the transmission of the packet data traffic associated with theone or more other packet data services. Such packet filter may forexample be installed in a gateway. Further, such packet filter couldalso be installed in the UE, e.g., to selectively block the volumecharged uplink packet data traffic from the UE.

The indication allows for establishing packet data connectivity of theUE while at the same time avoiding undesirable costs for the subscriber.In particular, certain services which are not subject to volumecharging, e.g., a voice telephony service, a text based messagingservice, or an electronic book service, may remain accessible for theUE, while volume charged services or media components of a service whichare subject to volume charging, such as video, are blocked.

Further details of the concepts and exemplary implementations will nowbe explained with reference to the accompanying drawings.

FIG. 1 shows a block diagram for schematically illustrating an LTE basedcommunication network architecture for implementation of the concepts asoutlined above. As illustrated, the architecture provides an eNB 100,which is an exemplary base station of an access network 110, referred toas evolved UMTS Terrestrial Radio Access Network (E-UTRAN). Further thearchitecture provides a Mobility Management Entity (MME) 120, a ServingGateway (SGW) 150, a Packet Data Network Gateway (PGW) 160, a Policy andCharging Rules Function (PCRF), and a Home Subscriber Server (HSS) 180.Further, FIG. 1 illustrates elements of the IMS, in particular aTelephony Application Server (TAS) 210, an IP television applicationserver (IPTV-AS) 220, a Service Centralization and ContinuityApplication Server (SCC-AS) 230, and a Call Session Control Function(CSCF) 240.

The MME 120 may be responsible for controlling connectivity and managingmobility of UEs in the cellular network. The PCRF 170 may be responsiblefor policing and charging related functionalities, e.g., as specified in3GPP TS 23.203 V12.4.0 (2014-03). The eNB 100, SGW 150, and the PGW 160carry user plane data traffic of a UE 10. Between the eNB 100 and the UE10, the user plane data traffic is carried over the LTE radio interface.The user plane data traffic is packet based, in particular based on IPdata packets. Unless described otherwise below, the eNB 100, the MME120, the SGW 150, PGW 160, PCRF 170, and HSS 180 may operate asspecified by 3GPP, e.g., in 3GPP TS 23.401 V12.4.0 (2014-03) or 3GPP TS23.402 V12.4.0 (2014-03).

The IMS nodes are responsible for providing an controlling variouspacket data services in the wireless communication network. Examples ofsuch services are packet based voice telephony, packet based multimediatelephony, packet based text or multimedia messaging, or packet basedmobile television. In the illustrated architecture, it is assumed thatthe TAS 210 is responsible for providing packet based voice telephony,packet based multimedia telephony, and/or packet based text ormultimedia messaging and that the IPTV-AS 220 is responsible forproviding packet based mobile television. The SCC-AS 230 may beresponsible for centralized control of such services, e.g., with respectto termination of incoming CS or packets based calls, and for providingsession continuity, e.g., when the UE moves between different accesses,in particular between an access supporting CS services and an accesssupporting backed based services. The CSCF 240 may be responsible forcontrolling sessions of the services, e.g., with respect toestablishment of the session, modification of the session, or ending ofthe session. The CSCF 240 may for example act as a Serving CSCF (S-CSCF)for the UE 10, i.e., be located in the home network of the UE 10, orcould act as a proxy CSCF (P-CSCF) for the UE 10, i.e., be located in avisited network in which the UE 10 is roaming or in the home network.Unless explained otherwise in the following, the functionalities of theIMS nodes may correspond to those as specified in 3GPP TS 23.228V12.4.0.

As illustrated in FIG. 1, various interfaces are provided to allowcommunication in the architecture of FIG. 1. For communication betweenthe UE 10 and the eNB 100, a radio interface referred to as Uu isprovided. For communication between the eNB 100 and the SGW 150, aninterface referred to as S1-U is provided. For communication between theSGW 150 and the PGW 160, an interface referred to as S5/S8 is provided.For communication between the eNB 100 and the MME 120, an interfacereferred to as S1-MME is provided. For communication between the MME 120and the SGW 150, an interface referred to as S11 is provided. Forcommunication between the MME 120 and the HSS 180, an interface referredto as S6a is provided. For communication between the PCRF 170 and theSGW 150, an interface referred to as Gxc is provided. For communicationbetween the PCRF 170 and the PGW 160, an interface referred to as Gx isprovided. For communication between the PCRF 170 and the HSS 180, aninterface referred to as Sp is provided. For communication between theHSS 180 and the SCC-AS 230, an interface referred to as Sh is provided.For communication between the HSS 180 and the CSCF 240, an interfacereferred to as Cx is provided. For communication between the CSCF 240and the application servers, i.e., the TAS 210, the SCC AS 230, and theIPTV-AS 220, an interface referred to as ISC is provided. Further, FIG.1 illustrates an interface between the UE 10 and the applicationservers, which is referred to as Ut, and an interface between the UE 10and the CSCF 240, which is referred to as Gm (between UE 10 and theP-CSCF) and Mw (between the P-CSCF and S-CSCF). These interfaces may beimplemented as for example specified in 3GPP TS 23.203 V12.4.0, 3GPP TS23.228 V12.4.0, 3GPP TS 23.401 V12.4.0, and 3GPP TS 23.402 V12.4.0. Inaccordance with the concepts as illustrated herein, some of theseinterfaces may be supplemented with a capability to transmit theabove-mentioned indication that a limitation of volume charged packetdata services is required.

In the following implementations of the concepts based on the indicationthat a limitation of volume charged packet data services is requiredwill be explained in more detail with reference to the architecture asillustrated in FIG. 1 and exemplary processes. In these processes, it isassumed that the indication relates to IMS services and has the form “novolume charged IMS services”, which may be provided as an additionalinformation element in some of the illustrated messages. However, itshould be understood that in other implementations, the indication couldalso refer to other volume charged packet data services or to volumecharged services in general. Accordingly, the indication will also bereferred to as “data off” indication. The indication may also furtherspecify that its applies only when the UE is roaming, i.e., be a “dataoff when roaming” indication. In some implementations, the indicationmay also specify an access network in which it is applicable, e.g., thatthe indication is applicable to LTE access, but not to 2G or 3Gaccesses, such as GSM or UMTS. The latter additional attributes allowfor deciding on the network side whether the indication should beapplied for preventing volume charged packet data traffic. In this way,it can be avoided that the UE 10 needs to update the indication whenchanging status, e.g., between roaming to non-roaming or between LTE andanother access network, e.g., based on GSM, UMTS, or WLAN (WirelessLocal Area Network).

FIG. 2 illustrates exemplary processes in which an IMS node uses theindication for preventing transmission of volume charged packet datatraffic while allowing other packet data traffic. The processes of FIG.2 involve the UE 10, the HSS 180, an application server (AS), such asthe TAS 210, SCC AS 230, or IPTV-AS 220, and the CSCF 240. In theprocesses of FIG. 2, it is assumed that the UE 10 has established a PDNconnection to the wireless communication network, using the IMS APN. TheUE 10 may be in its home network or in a visited network.

By sending message 201 to the CSCF 240, the UE 10 registers in the IMS.Message 201 may be a message of the Session Initiation Protocol (SIP) asspecified in IETF RFC 3261. The message 201 may be conveyed to the CSCF240 via the Gm/Mw interface. The message 201 includes the “data off”indication, which is stored by the CSCF 240.

The CSCF 240 may then query the HSS 180 for subscriber informationrelated to the UE 10, by sending message 202 to the HSS 180. Further,message 202 may include information for updating the HSS 180. Forexample, such information may indicate the presence of the “data off”indication, and the HSS 180 could this information for futureutilization. Message 202 may correspond to a Cx Put/Pull message. Inmessage 203, the HSS 180 responds with the subscriber information. Themessages 202 and 203 may be transmitted over the Cx interface betweenthe HSS 180 and the CSCF 240.

At some point, the UE 10 may request an IMS service, by sending message204 to the CSCF 240. Message 204 may be a SIP message transmittedbetween the UE 10 and the CSCF 240. As illustrated, message 204 may be aSIP request. For example, the UE 10 may request establishment of a voicecall by the TAS 210, may request establishment of a video call by theTAS 210, or may request establishment of a mobile television session bythe IPTV-AS 220. Upon receiving the message 204, the CSCF 240 may forexample perform processes for authorizing the requested IMS service.

In message 205, the CSCF 240 forwards the request of message 204 to theAS 210, 220. In message 205, the CSCF 240 may indicate whether therequested service is authorized and also which media components of theservice are authorized. This information may depend on the “data off”indication from the UE 10. For example, if the service is completelybased on volume charged packet data traffic, the CSCF 240 may decide tonot authorize the requested service. Further, if the service ispartially based on volume charged packet data traffic, the CSCF 240 maydecide to authorize only media components which are not subject tovolume charging. Still further, if the service is completely based onpacket data traffic which is not subject to volume charging, it maydecide to authorize the service with all media components. Asillustrated, also the “data off” indication may be forwarded in message205. This allows the AS 210, 220, 230 to decide whether the service orcomponents thereof are allowable or not.

As illustrated, message 205 may be a SIP request. The AS 210, 220, 230responds to the request of message 205 by sending message 206, which maybe a SIP response, to the CSCF 240.

In particular, the AS 210, 220, 230 may decide to reject the request ofmessage 205. This may for example be the case if the information inmessage 205 indicates that the service or all media components of theservice are not authorized. Further, the AS 210, 220, 230 may take thisdecision on the basis of the “data off” indication, even if at leastsome components of the service are authorized by the CSCF 240. Further,the AS 210, 220, 230 may accept the request of message 205. This may forexample be the case if the information in message 205 indicates that theservice or at least some media components of the service are authorized.On the basis of the response in message 206, the CSCF 240 sends message207 to the UE 10 to indicate the result of the decision by the AS 210,220, 230 and/or by the CSCF 240. As illustrated, message 207 may be aSIP response message.

If at least some media components of the service are authorized, the AS210, 220, 230 may then continue with the provision of the service to theUE 10, e.g., by sending packet data traffic associated with the serviceto the UE 10 and/or receiving packet data traffic associated with theservice from the UE 10.

The following exemplary rules may be applied in the processes of FIG. 2:If the “data off” indication was provided by the UE 10, the IMS node210, 220, 230, 240 responsible for the decision may disallow serviceswith video media and filer transfers, but allow voice media and textmessaging. As an alternative to disallowing all video media, the IMSnode 210, 220, 230, 240 may allow certain video media which is notsubject to volume charging, such as video media according to GSMA IR.94V.5.0 (Mar. 4, 2013). If the “data off” indication is not provided bythe UE 10, the IMS node 210, 220, 230, 240 may allow services and mediacomponents of these services, provided that there are no other reasonsfor disallowing some service or media components thereof.

The AS 210, 220, 230 may for example implement such policy byinactivating a disallowed media component, e.g., by modifying SessionDescription Protocol (SDP) information of the requested service. Forexample, the TAS 210 may inactivate video media from a request toestablish a video call. Further, as mentioned above, the AS 210, 220,230 may also reject requests, e.g., requests for file transfer or videotransmission. For example, the IPTV-AS 220 could reject a request forstreaming a video. In the case of rejecting a request, the originator ofthe request may be informed about the reason of rejection. In theexemplary scenario of FIG. 2, the UE 10 is the originator of the requestof message 204 and may thus be informed of the rejection (and itsreason) in message 207. However, it should be understood that in somecases the request for a service may also come from other entities thanthe UE 10. For example, in the case of a incoming call to be terminatedat the UE 10, the request could originate from another AS. The CSCF 240may implement such policy by not authorizing and inactivating servicesor media components of services which are subject to volume charging.For example, the CSCF 240 may authorize voice media and inactivate othermedia components, such as video. In some scenarios, it is also possiblethat separate nodes implement different parts of such policy. Forexample, an AS that handles voice and video calls may implement only thevideo related part of the policy, and another AS may implement the filetransfer related part of the policy.

In the exemplary processes of FIG. 2, the “data off” indication isprovided at IMS registration over the Gm/Mw interface. Alternatively orin addition, the “data off” indication could also be provided or updatedover the Ut interface, i.e., directly to the AS 210, 220, 230. Forexample, the UE 10 may update the indication when changing betweenroaming and non-roaming status. Further, while in the processes of FIG.2 the AS 210, 220, 230 may receive the “data off” indication from theCSCF 240 when an IMS service is requested, it would also be possiblethat the CSCF 240 already informs the AS 210, 220, 230 of the “data off”indication at IMS registration, similar to the HSS 180. Further, the AS210, 220, 230 could also obtain the information concerning the “dataoff” indication from the HSS 180.

FIG. 3 illustrates exemplary processes in which the indication isapplied by one or more in a policy and charging control (PCC) nodes ofthe communication network for preventing transmission of volume chargedpacket data traffic while allowing other packet data traffic. Theprocesses of FIG. 3 involve the UE 10, the eNB 100, the MME 120, the SGW150, the PGW 160, the PCRF 170, and the HSS 180. In the processes ofFIG. 3, the UE 10 initially attaches to the wireless communicationnetwork to establish a PDN connection.

At step 301, the UE 10 powers on. This is assumed to occur the coverageregion of a cell served by the eNB 100. Having selected this cell, theUE 10 continues by performing a random access procedure, as illustratedby step 302, and setting up a RRC (Radio Resource Control) connection.The RRC setup procedure involves that the UE 10 sends a message 303,referred to as RRCConnectionRequest, to the eNB 100, and that the eNB100 responds with a message 304, referred to as RRCConnectionSetup. TheUE 10 then sends message 305, referred to as RRCConnectionSetupComplete,to the eNB 100. The RRCConnectionSetupComplete message 305 includesinitial NAS (Non Access Stratum) information to be provided to the eNB100, in the present illustrated example a NAS Attach Request. The NASattach request includes the above-mentioned “data off” indication.Details concerning the RRC connection procedure may be as for examplespecified in 3GPP TS 36.331 V12.1.0 (2014-03). Details of the NAS attachprocedure and associated messages may be as for example specified in3GPP TS 23.401 V12.4.0.

The eNB 100 forwards the initial NAS information, i.e., the NAS attachrequest with the “data off” indication, to the MME 120.

As illustrated by 307, the MME 120 may then update the HSS 180. This mayinvolve sending an Update Location Request, e.g., as specified in 3GPPTS 23.401. This may also involve updating the HSS 180 with theinformation that the UE 10 provided the “data off” indication.

Further, the MME 120 sends a Create Session Request via the SGW 150 tothe PGW 160, as illustrated by messages 308 and 309. In the illustratedimplementation, the Create Session Request is used to forward the “dataoff” indication to the SGW 150 and PGW 160. Otherwise, the CreateSession Request may be as specified in 3GPP TS 23.401 V12.4.0.

In the exemplary processes of FIG. 3, it is assumed that dynamic PCC isused. Accordingly, the PGW 160 contacts the PCRF 170 to create a policycontrol session over the Gx interface. In the exemplary procedures ofFIG. 3, this is assumed to involve sending a Credit Control Request(CCR) 310 from the PGW 160 to the PCRF 170. By means of the CCR 310, the“data off” indication is forwarded to the PCRF 170. Depending on theindication, the PCRF 170 determines a PCC rule, according to whichpacket data traffic subject to volume charging is blocked for the UE 10,while other packet data traffic is allowed. In the following, this PCCrule will also be referred to as “data off” (DO) policy. This DO policymay in particular indicate or be used to configure a packet filter whichblocks the volume charged packet data traffic and passes other packetdata traffic. Such packet filter may be implemented as a correspondinglyconfigured traffic flow template (TFT), as for example specified in 3GPPTS 23.060 V12.4.0 (2014-03). The DO policy or packet filter may also bedetermined in an APN specific manner. That is to say, different APNs maybe associated with different APN policies. For example, only for the IMSAPN some packet data traffic not subject to volume charging may beallowed, while for other APNs all packet data traffic is blocked whenthe “data off” indication is provided by the UE 10.

The PCRF 170 then responds to the CCR 310 by sending a Credit ControlAnswer (CCA) 311 to the PGW 160. The CCA 311 is also used to indicatethe DO policy to the PGW 160. As illustrated by step 312, the PGW 160may implement the DO policy by installing the corresponding packetfilter. Alternatively, the PGW 160 may configure an existing packetfilter in accordance with the indicated DO policy.

The PGW 160 then sends a Create Session Response via the SGW 150 to theMME 120, as illustrated by messages 313 and 315. In the illustratedimplementation, the Create Session Response is used to forward the DOpolicy to the SGW 150 and to the MME 120. Otherwise, the Create SessionResponse may be as specified in 3GPP TS 23.401 V12.4.0. Having receivedmessage 313, i.e., the Create Session Response with the DO policy, theSGW 150 may install the corresponding packet filter, as indicated bystep 314.

The MME 120 then sends a Context Setup Request to the eNB 100, asindicated by message 316. The Context Setup Request is used to forwardthe DO policy to the eNB 100. Otherwise, the Context Setup Request maybe as specified in 3GPP TS 23.401 V12.4.0.

The eNB 100 then sends an RRCConnectionReconfig message 317 to the UE10. The RRCConnectionReconfig message 317 may for example be inaccordance with 3GPP TS 36.331 V12.1.0. The RRCConnectionReconfigmessage 317 includes a NAS Attach Accept message which is a response tothe NAS Attach Request in the RRCConnectionSetupComplete message 305.The NAs Attach Request is used for forwarding the DO policy to the UE10.

Having received the RRCConnectionReconfig message 317 with the DOpolicy, the UE 10 may install the corresponding packet filter, asindicated by step 318.

It is to be understood that further processes, not illustrated in FIG.3, may be part of a typical initial attach procedure, such as specifiedin 3GPP TS 23.401 V12.4.0. For example, processes for configuring thedefault bearer or an additional bearer may be included. Further, ratherthan using dynamic PCC mechanisms, the DO policy could also bestatically or preconfigured in the UE 10, SGW 150, and/or PGW 160, e.g.,by a management procedure. Such preconfigured DO policy may be activatedwhen the “data off” indication is provided by the UE 10.

In some scenarios, the UE 10 may use different APNs, each for differentservices. Accordingly, a new PDN connection may need to be establishedfor some services. FIG. 4 illustrates exemplary processes which use aPCC mechanism similar to the processes of FIG. 3, but in which the “dataoff” indication is provided in a PDN connection establishment procedure.The processes of FIG. 4 involve the UE 10, the MME 120, the SGW 150, thePGW 160, and the PCRF 170.

To establish the PDN connection, the UE 10 sends a PDN ConnectivityRequest 401. The PDN Connectivity Request is used for providing the“data off” indication to the MME 120. Otherwise, the PDN ConnectivityRequest may be as for example specified in 3GPP TS 23.401 V12.4.0.

The MME 120 then sends a Create Session Request via the SGW 150 to thePGW 160, as illustrated by messages 402 and 403. In the illustratedimplementation, the Create Session Request is used to forward the “dataoff” indication to the SGW 150 and the PGW 160. Otherwise, the CreateSession Request may be as specified in 3GPP TS 23.401 V12.4.0.

The PGW 160 the contacts the PCRF 170 to create a policy control sessionover the Gx interface for the new PDN connection. In the exemplaryprocedures of FIG. 4, this is assumed to involve sending aAuthentication/Authorization Request (AAR) 404 from the PGW 160 to thePCRF 170. By means of the AAR 310, the “data off” indication isforwarded to the PCRF 170. Depending on the indication, the PCRF 170determines a PCC rule, according to which packet data traffic subject tovolume charging is blocked for the UE 10, while other packet datatraffic is allowed, i.e., a DO policy. This DO policy may in particularindicate or be used to configure a packet filter which blocks the volumecharged packet data traffic and passes other packet data traffic. Suchpacket filter may be implemented as a correspondingly configured TFT.The DO policy or packet filter may also be determined in an APN specificmanner. That is to say, different APNs may be associated with differentAPN policies. For example, for one APN certain packet data traffic notsubject to volume charging may be allowed, while for other APNs otherpacket data traffic not subject to volume charging may be allowed.

The PCRF 170 then responds to the AAR 404 by sending anAuthentication/Authorization Answer (AAA) 405 to the PGW 160. The AAA405 is also used to indicate the DO policy to the PGW 160. Asillustrated by step 406, the PGW 160 may implement the DO policy byinstalling the corresponding packet filter. Alternatively, the PGW 160may configure an existing packet filter in accordance with the indicatedDO policy.

The PGW 160 then sends a Create Session Response via the SGW 150 to theMME 120, as illustrated by messages 407 and 409. In the illustratedimplementation, the Create Session Response is used to forward the DOpolicy to the SGW 150 and to the MME 120. Otherwise, the Create SessionResponse may be as specified in 3GPP TS 23.401 V12.4.0. Having receivedmessage 407, i.e., the Create Session Response with the DO policy, theSGW 150 may install the corresponding packet filter, as indicated bystep 408.

The MME 120 then sends a PDN Connectivity Accept message 410 UE 10. ThePDN Connectivity Accept message 410 is used to forward the DO policy tothe UE 10. Otherwise, the PDN Connectivity Accept message 410 may be asspecified in 3GPP TS 23.401 V12.4.0.

Having received the PDN Connectivity Accept message 410 with the DOpolicy, the UE 10 may install the corresponding packet filter, asindicated by step 410.

Further, the UE 10 may send a PDN Connectivity Complete message 413 tothe MME 120, thereby confirming establishment of the new PDN connection.The MME 120 may then send a Modify Bearer Request 413 to the SGW 150,which the SGW 150 may confirm by sending a Modify Bearer Response 414.These procedures may for example be as specified in 3GPP TS 23.401.

Also in the processes of FIG. 4, a preconfigured DO policy could be usedin place of the dynamically DO policy.

After having provided the “data off” indication, the state of the UE 10may change to a normal state, in which full packet data connectivity ofthe UE 10 is desired. Also this change of the “data off” indication maybe indicated by the UE 10 to the wireless communication network. Inscenarios where the prevention of the transmission of volume chargeddata traffic is implemented by an IMS node, such as in the processes ofFIG. 2, this may be achieved by an update procedure initiated by the UE10, e.g., by a Tracking Area Update. In scenarios where the preventionof the transmission of volume charged data traffic is implemented by aDO policy, such as in the processes of FIG. 3 or 4, this may be achievedby the UE 10 sending a request or other message to the MME 120. In thisrequest, the change of the “data off” state may be indicated implicitly,by not including the “data off” indication, or may be indicated by anexplicit “data on” indication. The MME 120 may then forward thisinformation to the SGW 150, PGW 160 and PCRF 170, by sending a ModifyBearer Request which includes a corresponding indication (or in whichthe “data off” indication is omitted).

FIG. 5 shows a flowchart for illustrating a method of controlling packetdata connectivity in a wireless communication network. The method ofFIG. 5 may be used for implementing the above concepts in a node of thewireless communication network, in particular in a node which isresponsible for providing a packet data service, e.g. an applicationserver such as the TAS 210, the IPTV-AS 220, or the SCC-AS 230, or in anode which is responsible for authorizing a packet data service, e.g., aCSCF such as the CSCF 240. If a processor based implementation of thenode is used, the steps of the method may be performed by one or moreprocessors of the node. For this purpose, the processor(s) may executecorrespondingly configured program code. Further, at least some of thecorresponding functionalities may be hardwired in the processor(s).

At step 510, the node receives an indication from a UE, e.g., from theUE 10. The indication indicates that a limitation of volume chargedpacket data services is required for the UE. The indication may indicatethat none of the volume charged packet data services are allowed for theUE, such as the above-mentioned “data off” indication. Alternatively,the indication may indicate that none of the volume charged packet dataservices are allowed while the UE 10 is roaming, such as theabove-mentioned “data off when roaming” indication. In someimplementations, the indication may further indicate one or more accessnetworks in which the indication is applicable, e.g., that theindication is applicable for LTE access networks, but not for 2G or 3Gaccess networks. The volume charged services may for example correspondto services of an IMS of the wireless communication system. Theindication may be provided in a procedure for registering for the volumecharged packet data services, e.g., during IMS registration or in aprocedure of updating IMS registration.

Depending on the received indication, the node prevents transmission ofpacket data traffic associated with the volume charged packet dataservices and allows transmission of packet data traffic associated withone or more other packet data services. In the method of FIG. 5, thisinvolves that the node controls provision or authorization of at leastone of the volume charged packet data services in accordance with thereceived indication.

In particular, at step 520 the node may receive a request associatedwith at least one of the volume charged packet data services. Forexample, the node may be an application server which is responsible forproviding the at least one volume charged packet data service, such asone of the application servers 210, 220, 230, and the request may be arequest for establishing a session of the at least one volume chargedpacket data service. An example of such request is the SIP request 204in the processes of FIG. 2. Alternatively, the node may be a controlserver which is responsible for authorizing the at least one volumecharged packet data service, such as the CSCF 240, and the request maybe a request for authorization of a session of the volume charged packetdata service. An example of such request is the SIP request 205 in theprocesses of FIG. 2.

At step 530, in response to the indication provided by the UE, the nodeprevents the transmission of the packet data traffic associated with theat least one volume charged packet data service. For this purpose, thenode may reject the request of step 520 or inactivate a media componentof the at least one of the volume charged service requested for the UE.

FIG. 6 shows a flowchart for illustrating a further method ofcontrolling packet data connectivity. The method of FIG. 6 may be usedfor implementing the above concepts in a node of a wirelesscommunication network, in particular in a node which is responsible forcontrolling packet data traffic, e.g., a gateway such as the SGW 150 orPGW 150, or a policy controller, such as the PCRF 170. If a processorbased implementation of the node is used, the steps of the method may beperformed by one or more processors of the node. For this purpose, theprocessor(s) may execute correspondingly configured program code.Further, at least some of the corresponding functionalities may behardwired in the processor(s).

At step 610, the node receives an indication from a UE, e.g., from theUE 10. The indication indicates that a limitation of volume chargedpacket data services is required for the UE. The indication may indicatethat none of the volume charged packet data services are allowed for theUE, such as the above-mentioned “data off” indication. Alternatively,the indication may indicate that none of the volume charged packet dataservices are allowed while the UE 10 is roaming, such as theabove-mentioned “data off when roaming” indication. In someimplementations, the indication may further indicate one or more accessnetworks in which the indication is applicable, e.g., that theindication is applicable for LTE access networks, but not for 2G or 3Gaccess networks. The volume charged services may for example correspondto services of an IMS of the wireless communication system. The node mayreceive the indication in a request of a procedure for attaching the UEto the wireless communication network. Alternatively or in addition, thenode may receive the indication in a request of a procedure forconfiguring packet data network connectivity between the UE and thewireless communication network.

Depending on the received indication, the node prevents transmission ofpacket data traffic associated with the volume charged packet dataservices and allows transmission of packet data traffic associated withone or more other packet data services. In the method of FIG. 6, thisinvolves that the node controls traffic handling in the wirelesscommunication network, e.g., using a PCC mechanism.

In particular, at step 620 the node may configure at least one packetfilter to prevent the transmission of the data traffic associated withthe volume charged packet data services. The at least one packet filterblocks the packet data traffic associated with the volume charged packetdata services and passes the packet data traffic associated with the oneor more other packet data services. The at least one packet filter mayoperate in the node. That is to say, the node may also install the atleast one packet filter, as indicated by step 630. For example, the PGW160 could configure and locally install the at least one packet filter.Alternatively or in addition, the at least one packet filter may operatein a further node of the wireless communication network. The node maythen indicate the at least one packet filter to such further node, asindicated by step 640. For example, the node may correspond to the PCRF170 and indicate the at least one packet filter to the PGW 160 and/orSGW 150. Alternatively or in addition, the at least one packet filtermay operate in the UE. The node may then indicate the at least onepacket filter to the UE, as indicated by step 640. For example, the nodemay correspond to the PCRF 170, PGW 160, or SGW 150, and indicate thepacket filter to the UE 10.

FIG. 7 shows a flowchart for illustrating a further method ofcontrolling packet data connectivity. The method of FIG. 7 may be usedfor implementing the above concepts in a UE, such as the UE 10. If aprocessor based implementation of the UE is used, the steps of themethod may be performed by one or more processors of the UE. For thispurpose, the processor(s) may execute correspondingly configured programcode. Further, at least some of the corresponding functionalities may behardwired in the processor(s).

At step 710, the UE detects a command to switch off packet dataconnectivity of the UE. This command may be based on a user selection,e.g., a selection of “data off” or “data off when roaming”.Alternatively, this command could be generated by an automatic processin the UE, e.g., a scheduled switching between “data off” and “data on”states or a process in which the command is triggered by a mobilityevent, such as entry of a visited network or attaching to a certainaccess network, such as an LTE access network.

At step 720, in response to the command of step 720, the UE sends anindication to the wireless communication network. The indicationindicates that a limitation of volume charged packet data services isrequired for the UE. The indication may indicate that none of the volumecharged packet data services are allowed for the UE, such as theabove-mentioned “data off” indication. Alternatively, the indication mayindicate that none of the volume charged packet data services areallowed while the UE 10 is roaming, such as the above-mentioned “dataoff when roaming” indication. In some implementations, the indicationmay further indicate one or more access networks in which the indicationis applicable, e.g., that the indication is applicable for LTE accessnetworks, but not for 2G or 3G access networks. The volume chargedservices may for example correspond to services of an IMS of thewireless communication system. The UE may send the indication in arequest of a procedure for attaching the user equipment to the wirelesscommunication network. Alternatively or in addition, the UE may send theindication in a procedure for configuring packet data networkconnectivity between the UE and the wireless communication network.Still further, the UE may send the indication in a procedure forregistering the UE for at least one of the volume charged packet dataservices.

At step 730, in response to sending the indication, the UE may receivean indication of a packet filter and install the packet filter at step740. The packet filter blocks the packet data traffic associated withthe volume charged packet data services and passing the packet datatraffic associated with the one or more other packet data services.

FIG. 8 illustrates exemplary structures for implementing the aboveconcepts in a node of a wireless communication network. For example, theillustrated structures may be used to implement an application server,e.g., an IMS application server such as the TAS 210, the IPTV-AS 220, orthe SCC-AS 230, or a control function related to a packet data service,such as the CSCF 240.

In the illustrated example, the node includes an interface 810 forproviding or controlling a packet data service. For example, theinterface 810 may correspond to a SIP based interface, such as Gm or Mwinterface as illustrated in the architecture of FIG. 1.

Further, the node includes one or more processor(s) 850 coupled to theinterface 810, and a memory 860 coupled to the processor(s) 850. Thememory 860 may include a read-only memory (ROM), e.g., a flash ROM, arandom access memory (RAM), e.g., a dynamic RAM (DRAM) or static RAM(SRAM), a mass storage, e.g., a hard disk or solid state disk, or thelike. The memory 860 includes suitably configured program code modulesto be executed by the processor(s) 850 so as to implement theabove-described functionalities of the node, e.g., corresponding to themethod steps of FIG. 5. More specifically, the program code modules inthe memory 860 may include a service handling module 870 so as toimplement the above-described functionalities of providing orauthorizing the packet data service. Further, the program code modulesin the memory 860 may include a communication module 880 so as toimplement the above-described functionalities of receiving the “dataoff” indication. Still further, the memory 860 may include a “data off”policy handling module 890 so as to implement the above-mentionedfunctionalities of selectively preventing the transmission of the packetdata traffic subject to volume charging in response to receiving the“data off” indication, e.g., by rejecting a request associated with thepacket data service subject to volume charging or inactivating a mediacomponent of the packet data service.

It is to be understood that the structures as illustrated in FIG. 8 aremerely schematic and that the node may actually include furthercomponents which, for the sake of clarity, have not been illustrated,e.g., further interfaces or further processors. Also, it is to beunderstood that the memory 860 may include further types of program codemodules, which have not been illustrated, e.g., program code modules forimplementing known functionalities of an application server or controlserver, such as an IMS application server or CSCF. In someimplementations, also a computer program may be provided forimplementing functionalities of the node, e.g., in the form of aphysical medium storing the program code modules to be stored in thememory 860 or by making such program code available for download orstreaming.

FIG. 9 illustrates exemplary structures for implementing the aboveconcepts in a node of a cellular network. For example, the illustratedstructures may be used to implement a node which controls handling ofuser plane traffic, e.g., a PCC node such as the SGW 150, the PGW 160,or the PCRF 170.

In the illustrated example, the node includes a first traffic interface910 for communication with one or more UEs and a second trafficinterface 920 for communication with other network nodes. The first andsecond interfaces 910, 920 may in particular have the purpose ofconveying user plane traffic of one or more UEs, such as the UE 10.Further, the node includes a control interface 930, which may be usedfor controlling the handling of user plane traffic. If the nodecorresponds to a PGW, such as the PGW 160, the control interface 930 maycorrespond to the Gx interface as illustrated in the architecture ofFIG. 1. If the node corresponds to an SGW, such as the SGW 150, thecontrol interface 930 may correspond to the Gxc interface as illustratedin the architecture of FIG. 1. If the node corresponds to a policycontroller, such as the PCRF 170, the control interface 930 maycorrespond to the Gx and/or Gxc interface as illustrated in thearchitecture of FIG. 1. In the latter case, the traffic interfaces 910and 920 may be omitted.

Further, the node includes one or more processor(s) 950 coupled to theinterfaces 910, 920 and 930, and a memory 960 coupled to theprocessor(s) 950. The memory 960 may include a ROM, e.g., a flash ROM, aRAM, e.g., a DRAM or SRAM, a mass storage, e.g., a hard disk or solidstate disk, or the like. The memory 960 includes suitably configuredprogram code modules to be executed by the processor(s) 950 so as toimplement the above-described functionalities of the node, e.g.,corresponding to the method steps of FIG. 6. More specifically, theprogram code modules in the memory 960 may include a PCC module 970 soas to implement functionalities of controlling the handling of userplane traffic of one or more UEs, e.g., on the basis of a PCC mechanism.Further, the program code modules in the memory 960 may include acommunication module 980 so as to implement the above-describedfunctionalities of receiving the “data off” indication. Still further,the memory 960 may include a “data off” policy handling module 990 so asto implement the above-mentioned functionalities of selectivelypreventing the transmission of the packet data traffic subject to volumecharging in response to receiving the “data off” indication, e.g., byconfiguring or installing at least one packet filter which blocks thepacket data traffic associated with the volume charged packet dataservice while passing other packet data traffic.

It is to be understood that the structures as illustrated in FIG. 9 aremerely schematic and that the node may actually include furthercomponents which, for the sake of clarity, have not been illustrated,e.g., further interfaces or further processors. Also, it is to beunderstood that the memory 960 may include further types of program codemodules, which have not been illustrated, e.g., program code modules forimplementing known functionalities of a PCC node, such as an PCRF, PGW,or SGW. In some implementations, also a computer program may be providedfor implementing functionalities of the node, e.g., in the form of aphysical medium storing the program code modules to be stored in thememory 960 or by making such program code available for download orstreaming.

FIG. 10 illustrates exemplary structures for implementing the aboveconcepts in a UE for a wireless communication network, such as the UE10.

In the illustrated example, the UE includes a radio interface 1010 forconnecting to the wireless communication network. The radio interface1010 may for example be based on a packet based cellular radiotechnology, such as the LTE radio access technology. As furtherillustrated, the UE may include a user interface 1020, e.g., based onkeys, a touch-sensitive surface, an optical display, and/or an acousticinput or output. The user interface 1020 may for example be used forselection of the “data off” state by a user of the UE.

Further, the node includes one or more processor(s) 1050 coupled to theradio interface 1010 and to the user interface 1020, and a memory 1060coupled to the processor(s) 1050. The memory 1060 may include a ROM,e.g., a flash ROM, a RAM, e.g., a DRAM or SRAM, a mass storage, e.g., ahard disk or solid state disk, or the like. The memory 1060 includessuitably configured program code modules to be executed by theprocessor(s) 1050 so as to implement the above-described functionalitiesof the UE, e.g., corresponding to the method steps of FIG. 7. Morespecifically, the program code modules in the memory 1060 may include a“data off” state management module 1070 so as to implementfunctionalities of managing selection of the “data off” state, e.g., inresponse to a user selection via the user interface 1020 or in responseto an automatic process, e.g., based on a schedule or triggering event.Further, the program code modules in the memory 1060 may include acommunication module 1080 so as to implement the above-describedfunctionalities of sending the “data off” indication. Still further, thememory 1060 may include a PCC module 1090 so as to implement theabove-mentioned functionalities of installing a packet filter whichblocks the packet data traffic associated with the volume charged packetdata service while passing other packet data traffic.

It is to be understood that the structures as illustrated in FIG. 10 aremerely schematic and that the UE may actually include further componentswhich, for the sake of clarity, have not been illustrated, e.g., furtherinterfaces or further processors. Also, it is to be understood that thememory 1060 may include further types of program code modules, whichhave not been illustrated, e.g., program code modules for implementingknown functionalities of a UE. In some implementations, also a computerprogram may be provided for implementing functionalities of the node,e.g., in the form of a physical medium storing the program code modulesto be stored in the memory 1060 or by making such program code availablefor download or streaming.

As can be seen, the concepts as described above may be used forefficiently controlling packet based connectivity in a wirelesscommunication network. In particular, the concepts may be used forallowing appropriate usage of an access which offers only packet basedconnectivity, such as an LTE access, while at the same time avoidingundesired volume-charged traffic.

It is to be understood that the examples and embodiments as explainedabove are merely illustrative and susceptible to various modifications.For example, the prevention of volume charged packet data trafficimplemented by an IMS node or the like, such as illustrated by theprocesses of FIG. 2, could be combined with the prevention of volumecharged traffic by a PCC mechanism, such as illustrated by the processesof FIGS. 3 and 4. Further, various mechanisms could be used forproviding the “data off” indication. For example, providing theindication during an attach procedure, as illustrated in FIG. 3, or aradio connectivity configuration procedure, as illustrated in FIG. 4,could also be used for conveying the indication to an IMS node byproviding the indication to the HSS 180, from where it can be retrievedby the IMS node. Similarly, providing the indication during IMSregistration or some other SIP procedure, as illustrated in FIG. 2,could also be used for conveying the indication to a PCC node byproviding the indication to the HSS 180, from where it can be retrievedby the PCC node.

Further, the illustrated concepts could be used in connection withvarious types of cellular network technologies, without limitation tothe above-mentioned LTE technology. Moreover, it is to be understoodthat the above concepts may be implemented by using correspondinglydesigned software to be executed by one or more processors of anexisting device or network node, or by using dedicated hardware.

1. A method of controlling packet data connectivity in a wirelesscommunication network, the method comprising: a node of the wirelesscommunication network receiving, from a user equipment, an indicationthat a limitation of volume charged packet data services is required forthe user equipment; and depending on the received indication, the nodepreventing transmission of packet data traffic associated with thevolume charged packet data services and allowing transmission of packetdata traffic associated with one or more other packet data services. 2.The method according to claim 1, wherein the indication indicates one of(A) that none of the volume charged packet data services are allowed forthe user equipment and (B) that none of the volume charged packet dataservices are allowed while the user equipment is roaming, and whereinthe indication further indicates one or more access networks in whichthe indication is applicable. 3-4. (canceled)
 5. The method of claim 1,further comprising: the node configuring at least one packet filterwhich blocks the packet data traffic associated with the volume chargedpacket data services and passes the packet data traffic associated withthe one or more other packet data services, wherein the at least onepacket filter operates in the user equipment. 6-8. (canceled)
 9. Themethod according to claim 5, wherein the node receives the indication inone of (A) a procedure for attaching the user equipment to the wirelesscommunication network and (B) a procedure for configuring packet datanetwork connectivity between the user equipment and the wirelesscommunication network. 10-12. (canceled)
 13. The method according toclaim 1, wherein the node prevents the transmission of the packet datatraffic associated with the at least one volume charged packet dataservice by at least one of (A) inactivating a media component of the atleast one of the volume charged packet data service and (B) rejecting arequest associated with the at least one volume charged packet dataservice.
 14. (canceled)
 15. The method according to claim 13, whereinthe node receives the indication in a procedure for registering the userequipment for the at least one volume charged packet data service. 16.(canceled)
 17. A method of controlling packet data connectivity in awireless communication network, the method comprising: a user equipmentdetecting a command to switch off packet data connectivity of the userequipment, in response to the command, the user equipment sending, tothe wireless communication network, an indication that a limitation ofvolume charged packet data services is required for the user equipment.18. The method according to claim 17, wherein the indication indicatesone of (A) that none of the volume charged packet data services areallowed for the user equipment and (B) that none of the volume chargedpacket data services are allowed while the user equipment is roaming,and wherein the indication further indicates one or more access networksin which the indication is applicable. 19-20. (canceled)
 21. The methodaccording to claim 17, wherein the user equipment sends the indicationin at least one of (A) a procedure for attaching the user equipment tothe wireless communication network (B) a procedure for configuringpacket data network connectivity between the user equipment and thewireless communication, and (C) a procedure for registering the userequipment for at least one of the volume charged packet data services.22-23. (canceled)
 24. The method according to claim 17, furthercomprising: in response to sending the indication, the user equipmentreceiving an indication of a packet filter; and the user equipmentinstalling the packet filter, the packet filter blocking the packet datatraffic associated with the volume charged packet data services andpassing the packet data traffic associated with the one or more otherpacket data services.
 25. (canceled)
 26. A node for a cellular network,the node comprising: at least one interface; and at least one processor,the at least one processor being configured to: receive, from a userequipment, an indication that a limitation of volume charged packet dataservices is required for the user equipment; and depending on thereceived indication, prevent transmission of packet data associated withthe volume charged packet data services and allowing transmission ofpacket data associated with one or more other packet data services. 27.The node according to claim 26, wherein the indication indicates one of(A) that none of the volume charged packet data services are allowed forthe user equipment and (B) that none of the volume charged packet dataservices are allowed while the user equipment is roaming, and furtherindicates one or more access networks in which the indication isapplicable. 28-29. (canceled)
 30. The node according to claim 26,wherein the at least one processor is configured to configure at leastone packet filter which blocks the packet data traffic associated withthe volume charged packet data services and passes the packet datatraffic associated with the one or more other packet data services, andwherein the packet filter operates in the user equipment.
 31. The nodeaccording to claim 30, wherein the packet filter operates in at leastone of (A) the node and (B) a further node of the wireless communicationnetwork. 32-33. (canceled)
 34. The node according to claim 30, whereinthe at least one processor is configured to receive the indication inone of (A) a procedure for attaching the user equipment to the wirelesscommunication network, and (B) a procedure for configuring packet datanetwork connectivity between the user equipment and the wirelesscommunication network.
 35. (canceled)
 36. The node according to claim26, wherein the node is one of (A) an application server which isresponsible for providing at least one of the volume charged packet dataservices and (B) a control server which is responsible for authorizingat least one of the volume charged packet data services.
 37. (canceled)38. The node according to claim 36, wherein the at least one processoris configured to prevent the transmission of the packet data trafficassociated with the at least one volume charged packet data service byat least one of (A) inactivating at a media component of the at leastone of the volume charged service and (B) rejecting a request associatedwith the at least one volume charged packet data service.
 39. (canceled)40. The node according to claim 36, wherein the at least one processoris configured to receive the indication in a procedure for registeringthe user equipment for the at least one volume charged packet dataservice. 41-42. (canceled)
 43. A user equipment, comprising: aninterface for connecting to a wireless communication network; and atleast one processor, the at least one processor being configured to:detect a command to switch off packet data connectivity of the userequipment, and in response to the command, send to the wirelesscommunication network an indication that a limitation of volume chargedpacket data services is required for the user equipment.
 44. The userequipment according to claim 43, wherein the indication indicates one of(A) that none of the volume charged packet data services are allowed forthe user equipment and (B) that none of the volume charged packet dataservices are allowed while the user equipment is roaming, and whereinthe indication further indicates one or more access networks in whichthe indication is applicable. 45-46. (canceled)
 47. The user equipmentaccording to claim 43, wherein the at least one processor is configuredto send the indication in a procedure for at least one of (A) attachingthe user equipment to the wireless communication network, (B)configuring packet data network connectivity between the user equipmentand the wireless communication network, and (C) registering the userequipment for at least one of the volume charged packet data services.48-49. (canceled)
 50. The user equipment according to claim 43, whereinthe at least one processor is configured to: in response to sending theindication, receive an indication of a packet filter, and install thepacket filter, the packet filter blocking the packet data trafficassociated with the volume charged packet data services and passes thepacket data traffic associated with the one or more other packet dataservices. 51-56. (canceled)